MacFormat 1995 March

home *** CD-ROM | disk | FTP | other *** search

/ MacFormat 1995 March / macformat-022.iso / Shareware City / Utilities / MacDOS™ 2.0.0ƒ / User's Guide / A.1 Errors (A-M) < prev next >

Wrap

Text File | 1994-11-23 | 25.9 KB | 565 lines | [TEXT/ttxt]

A Error Codes This section provides a full list of all error and warning messages displayed by MacDOS. The messages are listed in alphabetical order and preceded by the corresponding error or warning code. Note that the error codes are only visible when errors and warnings are reported with alert boxes (ie. after executing ALARM ON). If you detect a bug or an undocumented error, please inform Rainbow Hill immediately. Errors Attempted to open too many files (E32) MacDOS attempted to open more files that the Mac OS allows. This is usually due to a high "depth" of batch CALLs combined with file copying, output redirection, and logging. Suggested actions: • Reduce the maximum "depth" of batch CALLs by serialising calls whenever possible. If you are copying files within the "deepest" batch program, split the copying of data and resource forks into two separate commands. Bad command or file name (E41) MacDOS could not make sense of your command. You probably mistyped a command, or attempted to execute a program which MacDOS could not find. Perhaps you typed a "pipe" at the end of a command, attempted to run interactively a command which is only legal in batch mode, or typed a badly formatted command. Suggested actions: • Check that the command name is correct. • If you were trying to run a program, check whether the batch or application file exists. Also type the command PATH and check that it lists all the folders that you expect to find there. • If you typed a command, check that it is legal in interactive mode. • Check that you have not omitted any compulsory token in complex commands like IF, DECR, etc. • If you started the command with a MacDOS filter, check that you redirected its input. Bad switch (E28) You entered a command with a badly formatted switch. Suggested actions: • Use the on-line help to look at the switches supported by the command which failed. Command not implemented (E43) You attempted to use a DOS command which is not currently supported by MacDOS. Suggested actions: • Protest with Rainbow Hill. If we received enough protests, we might implement it in a future release. Command only executable in batch (E46) You typed a command which is only executable within a batch program. Currently, only GOTO, IF, NEXT, PAUSE, and SHIFT return this error. Suggested actions: • Re-examine what you intended to do and perhaps write a small batch program. Dimensioning: prompt too long (E15) You attempted to set a prompt longer than 199 characters. Do you really want to be prompted by a couple of lines of text after typing each command? Suggested actions: • Be sensible! Dimensioning: too many arguments (E6) You entered a command with 24 or more parameters and switches. Suggested actions: • Check whether some switches appear more than once and get rid of the duplicates. If there are no duplicates, could you please tell Rainbow Hill what command you typed? Dimensioning: too many commands (E5) MacDOS counted more than 8 commands separated by pipes in a single line. Suggested actions: • Break up the chain of piped filters by storing intermediate results into disk files. Dimensioning: too many tokens (E2) Your command line contained 64 tokens or more. Suggested actions: • This situation is very unlikely to occur, because MacDOS limits the input to a length of 199 characters. Please, inform Rainbow Hill of the command which caused the problem. Directory name missing (E23) You entered without parameters a command which expected a folder name as a parameter. Suggested actions: • Re-examine what you were trying to do. You probably typed MKDIR \ or RMDIR \ . If that is the case, remember that you cannot ever remove a root directory. Directory specified (E53) MacDOS found a directory when it expected to find a file. Suggested actions: • If you were executing an XCOPY command, you will find that a file in the source and a folder in the destination have the same name. XCOPY then returns this error when it attempts to replace the folder in the destination. Rename the file or remove the folder. Disk full (E80) MacDOS could not create or extend a file because there is not enough space on the requested volume. Note that when MacDOS needs to overwrite a file during aCOPY operation, it first creates a new file with a temporary name. Suggested actions: • Make some space by removing existing files. DOS command not implemented (E1) You attempted to use a DOS command which is not supported by MacDOS. Suggested actions: • Protest with Rainbow Hill, although the chances that you are going to get this command in a future release are slim. Double initialisation of pipes (E90, pipeDoubleInitErr) MacDOS attempted to initialise twice the pipe mechanism. This might be due to MacDOS' memory partition being corrupted. Suggested actions: • This situation should never occur. Start logging with LOG/O, attempt to reproduce the problem, and, if successful, send a listing of the log file to Rainbow Hill. • Quit and re-launch MacDOS. Duplicate file name and version (E48) Up to release 0.2.0, MacDOS returned this error whenever a File Manager call returned the Mac OS error -48 (dupFNErr). This occurs whenever one tries to rename a file or create a directory and an item with the same name in the same folder already exists. After 0.2.0 this errors have all been trapped with E58 Duplicate filename(s). Suggested actions: • Upgrade to the latest release or refer to E58. Duplicate filename(s) (E58) You attempted to create a directory or rename a file when an item with the same name and in the same folder already existed. Suggested actions: • Either you use a different name, or you rename the existing item, or you operate in a different folder. Error when following a path (E17) MacDOS could not follow a chain of folder names given in a command parameter. Suggested actions: • Check that you did not attempt to "back up" higher than the root directory of a particular volume. This happens when you type too many up-one-level-strings (ie. "..\") in a path. File already open for writing (E77) You attempted to OPEN a file already opened by another application in exclusive mode. Suggested actions: • Check that you correctly typed filename [and path]. • Check that you are not LOGging into that file and remember that only files opened with OPEN are listed when you type OPEN without parameters (ie. the file used for logging is opened internally by MacDOS and does not appear in the list). • If you are convinced that the file should be closed, quit the application which opened it last. That application might have erroneously left the file open (a bug). If in doubt, close all other applications before attempting to open the file with MacDOS. File busy, dir non empty, or path error (E49) MacDOS attempted to access or remove an open file or to remove a folder which was not empty. Suggested actions: • Check that no other application is using the file that you were trying to access. If this does not work, close all other applications, because some of them might have a bug and hold onto files. • If you got this error message while trying to remove a folder with RMDIR, empty it by deleting its content and then try to remove it once more. Note that the folder might contain an invisible file, like those used to show folders with custom icons. • If your command contained a path, check that it is correct: you might have been accessing an item with the correct name but in the wrong folder. File not opened by the user (E3) You attempted to access with READ or WRITE a file which you did not open with OPEN. Remember that MacDOS closes the file when you read past the EOF. Suggested actions: • Check that you typed the correct fileID and type OPEN without parameters to see whether some other files are open. • Open the file before attempting to access it again. File open for writing (E75) You attempted to READ from a file OPENed for writing. Suggested actions: • Check that you typed the correct fileID and type OPEN without parameters to see whether some other files are open. File open for reading (E74) You attempted to WRITE into a file OPENed for reading. Suggested actions: • Check that you typed the correct fileID and type OPEN without parameters to see whether some other files are open. File or directory not found (E27) MacDOS could not find the item you wanted to operate on. Suggested actions: • If your command contained a path, check that it specifies the correct folder: you might have been looking for something which exists somewhere else. • If you were specifying a wildcarded name, this error could simply mean that no name matched the wildcarding. Filter error (E70, pipeFilteringErr) During execution of a command containing pipes, one of the filters reported to MacDOS a generic error. Suggested actions: • If you are developing a filter, always try to report specific errors or at least associate a proprietary error message to the generic error code. Please refer to Appendix B for help. Filter sent a command that only MacDOS should issue (E92, pipeComFilterE) While performing a command containing pipes, MacDOS received from a filter a message of a type which is normally used by MacDOS itself to configure a chain of filters. Suggested actions: • You have probably used the wrong command code while modifying pipe.c or pipe.h. You should not modify those files. Please refer to Appendix B for help. Filter sent a data message out of a sequence (E93, pipeSequenceE) While performing a command containing pipes, MacDOS received a data message with an invalid sequence number. Suggested actions: • You have probably dropped a message in your filter. Remember that you have to forward to the outgoing pipe a message for each message that you receive from the incoming pipe. • If you were modifying pipe.c or pipe.h, you have probably corrupted the variable used for storing the last sequence number. You should not modify those files. Please refer to Appendix B for help. Filter sent downstream a message that should only be sent upstream (E101, pipeDownstreamErr) While performing a command containing pipes, MacDOS received an error message through the PPC port that should only deliver data messages. Suggested actions: • You have probably caused the problem by incorrectly updating pipe.c or pipe.h. You should not modify those files. Please refer to Appendix B for help. Filter sent upstream a message that should only be sent downstream (E100, pipeUpstreamErr) While performing a command containing pipes, MacDOS received a data message through the PPC port that should only deliver error messages. Suggested actions: • You have probably caused the problem by incorrectly updating pipe.c or pipe.h. You should not modify those files. Please refer to Appendix B for help. Folders named Desktop Folder and Trash cannot be created or removed (E73) These two names are reserved. Suggested actions: • Slightly change the name so that it becomes acceptable. Something like Desktop-Folder and Trash- Can would be ok. Remember that file and folder names are case insensitive. Therefore, changing to lower case would not help. The command cannot be piped (E79) You tried to pipe the output of something that does not allow output redirection (eg. an application or an AppleScript). You can pipe the output of a standard FOR, but only to the command MORE. Suggested actions: • You would probably achieve your purpose by redirecting the output to a file. You could then READ and operate on one line of text at a time within a batch program. • Check that you have not used a normal application in place of a MacDOS filter. Hardware volume lock (E51) MacDOS could not operate on an item because the volume had the "write-protect" switch ON. Suggested actions: • Check that you are operating on the correct volume and be sure that you know what you are doing. Usually, write protection has a reason to exist. If you really want to do it, eject the cartridge, remove its write protection, and re-insert it into the drive before repeating the command. I/O error in disk operation (E56) MacDOS could not complete a write or verify operation when copying or verifying a file. The number of bytes written or read back was lower than the number requested. The destination file was left corrupted. Suggested actions: • Attempt to save critical files to a different volume before doing anything else. • Reformat or run a diagnostic on the destination volume before using it again. Illegal wildcarding (E34) MacDOS was given a wildcarded filename when it expected to operate on an individual file. The most likely cause is that you specified a folder name as a parameter of a command which expected a file name. Then MacDOS attempted to operate on all files in the folder. Another possible explanation is that you passed a wildcarded filename to XCOPY (which only accepts folder names). Suggested actions: • Review what your intentions were and check whether you passed the correct type of parameters to the command you used. Internal I/O error (E33) MacDOS encountered an inconsistency when using internally defined global parameters. For example, it might have attempted to use an invalid file ID or a non- existing batch label. This might be due to MacDOS' memory partition being corrupted. Suggested actions: • This situation should never occur. Start logging with LOG/O, attempt to reproduce the problem, and, if successful, send a listing of the log file to Rainbow Hill. • Quit and re-launch MacDOS. Internal: unknown com state (E10) Internal: unknown token (E25) MacDOS encountered an unknown state or token while parsing a command. This is likely to be a case of corrupted memory. Suggested actions: • This situation should never occur. Please, inform Rainbow Hill of the command which caused the problem. Invalid date or date format (E47) Either you attempted to set an impossible date or date format, or a new date did not conform to the current date format. Suggested actions: • Check that year, month, and day were in the order specified by the current date format (eg. 03/25/96 exists in the USA but not in Australia). Also check that the separators were correct. • Check that the specified day exists (eg. 94/11/31 or 95/02/29 do not exist). • check that the year is in the interval 1904 to 2040. • If you were entering a new date format, check that you only used the characters Y, M, and D plus two special characters as separators. Invalid prompt switch (E14) MacDOS did not recognise all format specifications included in your PROMPT command. Suggested actions: • Ensure that each character immediately following a dollar sign is recognised by DOS as a format specification. Remember that you have to type two consecutive dollars if you want to include a '$' in your prompt. Invalid session reference number (E85, noSessionErr) During execution of a command containing pipes, one of the filters attempted to address a PPC session that was not initialised. Suggested actions: • You have probably caused the problem by incorrectly updating pipe.c or pipe.h. You should not modify those files. Please refer to Appendix B for help. Invalid time (E52) The new time given to MacDOS was wrong. Suggested actions: • Check that the specified time exists (eg. 13:20p, or 25:00 do not exist). Label not found (E44) While running in batch, MacDOS could not complete a command containing a label because it did not find the label in the current batch program. Suggested actions: • If the command that failed was a REPEAT, replace it with a GOTO. • If the command that failed was a GOTO, ensure that the destination label actually exists in the same batch file. • If you were executing a batch without echo, comment out the ECHO OFF command in the batch file in order to determine which command is causing the error. With ALARM ON, MacDOS actually tells you the name of the label which could not be found. Label used for more than one loop (E59) MacDOS found that two REPEAT commands contained the same label name. Suggested actions: • Replace the REPEATs with GOTOs. Labels are only allowed in batch mode (E96) You entered a label interactively. Suggested actions: • Just don't do it. In any case, what is the purpose of typing a label if you cannot use a GOTO to jump to it? Labels must not begin with a percent sign (E65) MacDOS found a label which begins with a percent sign. Suggested actions: • Change the offending label name. Licence number and/or user identification corrupted. Please reload MacDOS from the original disk. (E67) MacDOS could not decode the string which normally contains licence number and user name. Suggested actions: • Overwrite the faulty copy of MacDOS with that contained in the original disk. Line parsing error (E9) MacDOS could not parse the command line. Perhaps, you typed some non-printing characters. Suggested actions: • Retype the command (ie. do not recall it with up- arrow). If the problem persists, please report it to Rainbow Hill. MacDOS error ... (the dots indicate a number) An error message which provides a code instead of a message in clear should never occur. This indicates that the TEXT resource containing all error messages does not contain a message corresponding to the given code. Suggested actions: • Unless you have modified the TEXT resources of MacDOS, please report the problem to Rainbow Hill. MacDOS requires System 6.0.4 or greater (E38) MacDOS discovered that the system you are using on your Mac does not contain the Gestalt facility. This facility is necessary in order to properly configure MacDOS. Suggested actions: • Upgrade to the latest system 6 (ie. 6.0.8) or to system 7. MacOS error (E24) A system trap returned to MacDOS an error code for which MacDOS does not have a message in clear. Suggested actions: • If you liked MacDOS to be able to display a clear message rather than a mysterious number, please send the code to Rainbow Hill. Perhaps the next release of MacDOS will then respond to that error condition with a message in clear. If you decide to do so, please send together with the error code a description of the circumstances under which the error was reported. Max length of filename exceeded (E26) You specified a file or folder name longer than 31 characters. Suggested actions: • Use a shorter name. Maximum line length exceeded (E76) MacDOS detected a line of text longer than 199 characters. In batch, this might have happened after variable names where replaced with their content. Suggested actions: • Create new variables which only contain what is strictly necessary for the task at hand. • If your variables contain folder names, use CD to move down the path and use relative paths. Maximum number of directories exceeded (E20) MacDOS attempted to access a folder too deep. Only 31 levels of folders are supported by MacDOS. Suggested actions: • Attach to an intermediate folder, so that MacDOS does not need to go so deep. • Flatten the folder tree structure by moving one of the deepest folders up one level. For example, if folder A contains B which contains C, move C out of B so that both B and C are contained in A. Maximum number of volumes exceeded (E18) You attempted to handle more than 31 volumes simultaneously. Suggested actions: • Do you really need to have simultaneous access to more than 31 volumes? You can probably EJECT some of the volumes (which is equivalent to trashing the volume icons). Memory mode is 32-bit, but application is not 32-bit clean (E31) Suggested actions: • Change the memory mode or, better, remove the application from your system. Perhaps a new release of the same application is 32-bit clean. Mismatch when verifying data written to disk (E57) MacDOS found that the data read back in order to verify a copy operation did not match what was originally written. The destination file of the copy operation was corrupted. Suggested actions: • Attempt to save critical files to a different volume before doing anything else. • Re-format or run a diagnostic on the destination volume before using it again.